1 link tagged with all of: metastable failures + marc brooker + system behavior
Click any tag below to further narrow down your results
Links
AWS engineer Marc Brooker argues that software engineering's focus on reading code gets in the way of understanding what really matters: the behavior of the system as built. He says we need new tools, like the Bode plots or Nyquist criterion other engineering fields use, to grasp emergent properties such as metastable failures.
- Code-level understanding is a poor fit for system-level properties. Things like "a SELECT never shows uncommitted data" or "makes the user's life easier" emerge from the whole system, not individual lines.
- Emergent behaviors like metastable failures can't realistically be extracted from source code, in the same way the Lorenz attractor or a Julia set resists analysis from its equations alone.
- Software lacks the analytical tools other engineering disciplines have, and Brooker sees AI as a way to help build them. He also thinks the "No AI Slop" manifesto doesn't fully work out what "understanding" should mean.